One-Item-at-a-Time Rule

The One-Item-at-a-Time Rule is a discipline for processing incoming work: keep attention on the item in hand, decide what should happen to it, and move it out of the in-basket rather than letting distraction turn it into another unresolved pile. The rule is not a demand to finish every task immediately. It is a demand to make a decision about each item before moving on, so that incoming work becomes organized choices instead of a stack that keeps reclaiming attention.

The in-basket as a processing station

The rule belongs to a larger distinction between processing and storage. An in-basket is a processing station, not a place to keep material whose meaning or next step remains undecided. The recommended sequence is to process the top item first, handle one item at a time, and never return a processed item to the in-basket. The order in which the whole stack is cleared may vary: working from one end to the other within a reasonable period will bring all the items into view, while clearing a large backlog of email may be more efficient from the newest messages downward because discussion threads accumulate on top of one another. That flexibility in sequence does not change the one-item focus of each decision.

The rule also clarifies what “handle things once” can and cannot mean. Taken literally as a command to complete every item on first sight, it would leave no room for lists and would make people finish things immediately even when that is inefficient or inappropriate. Its useful meaning is more precise: when an item is first picked up for processing, decide what it means, what should be done about it, and where it belongs. Repeatedly lifting an item, postponing that decision, and putting it back into the same incoming stack is the habit the rule is designed to stop.

Why attention must stay with the item

The characteristic failure begins when an item proves difficult to interpret. Someone picks it up, does not yet know what to do, and lets their eyes wander to a later item that looks easier, more important, or more appealing. The first item is then likely to be abandoned in an informal side pile while attention shifts elsewhere. That detour may feel productive because the next item offers a clearer action, but it leaves the original decision unfinished and creates another place for work to disappear from view.

Taking a whole stack out of the in-basket at once creates a related risk. The desire to deal with a large chunk is understandable, but it scatters incoming material across the desk and makes it harder to regain control if an interruption occurs. Keeping all but the single top item in the tray limits that exposure. It also makes the processor give the item in hand the attention and decision-making it requires, rather than choosing among a spread of competing objects by convenience.

The emphasis is therefore not on speed for its own sake, nor on completing every task at once. It is on preventing unresolved input from multiplying into several visible and invisible queues. One item receives a decision; its destination is established; only then does attention move to the next. The clean boundary between incoming material and processed material is what makes the sequence manageable.

The exception and its limit

The rule allows a carefully limited exception for people who make decisions more easily by shifting their attention briefly. In such cases, the processor may take out two or sometimes three items at once, making it easier and faster to choose the action required. The exception is presented as a practical accommodation to differences in how people reach a decision, not as permission to work through an indiscriminate pile.

Its limit is explicit: multitasking must remain exceptional, every item must still be processed in short order, and no decision should be avoided for more than a minute or two. The distinction is between a brief comparison that helps a decision and an extended escape from one. If several items are kept out, they must not become a substitute in-basket scattered across the desk; the point remains to resolve each item and move it to an appropriate place.

From decision to action system

The discipline matters because knowledge work rarely arrives with clear edges. Projects may be improved indefinitely with readily available information, organizational outcomes increasingly depend on cross-divisional communication, and roles and responsibilities shift as organizations change. Under those conditions, people face large volumes of external communications and internal commitments without always having a reliable way to keep track of them. Processing one item at a time is one small but concrete behavior within a wider system intended to connect large-scale priorities to the smallest open details and to keep new inputs under control.

A decision about an item should lead to an actual organizational destination, not merely to the hope of remembering it. If an item requires action, the next step can be tracked in the appropriate action list; if it is waiting on another person, it can be recorded as something to follow up on. Actions that can happen as soon as possible are organized by context: a computer task belongs with computer actions, an errand requiring a car belongs with errands, and a conversation with a particular person belongs on that person’s agenda. The context is not just a filing convenience. Choosing it requires identifying what physical action comes next and what tool, location, or person is needed.

The same logic can be embodied in a simple physical cue. Someone who must take work home and bring it back the next morning can place it in front of the door or on their keys, making the object a reminder at the moment it is needed. The preparation anticipates that a person may be barely conscious first thing in the morning; the item is positioned so that it prompts the intended action rather than relying on memory alone. This is the same broader movement as processing an in-basket item: move the commitment out of an untrusted mental holding pattern and into a system or context that can prompt action.

Organizational significance

The rule is especially consequential in settings where communication travels through voicemail, email, conversations, and written notes. For an organization to rely on a request, the recipient’s system must capture it, process and organize it, and make it available for review as an option for action. If someone reliably manages only one medium, others must adapt to that limitation, and communication can become a weak link. An item left unprocessed is not merely a personal nuisance when other people depend on the commitment it represents.

Individual work systems cannot simply be legislated, but organizations can hold people accountable for outcomes and for tracking what comes their way. They can also cultivate the expectation that everyone may have more work than they can complete and that agreements about what will not be done must be renegotiated. Such renegotiation depends on retaining a reliable record: people cannot renegotiate a commitment they have forgotten making, or one with others that has slipped out of view. The one-item rule is a modest operational discipline, but it contributes to that larger reliability by ensuring that incoming work is decided and routed rather than repeatedly encountered and lost.